use PAT when pushing to homebrew repo - #177
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The current approach unnecessarily embeds the PAT into the clone remote for a public repo and uses a non-Azure logging command format for the new “PAT is empty” failure path.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Updates the Azure Pipelines release workflow so Homebrew tap updates authenticate using a GitHub Personal Access Token (PAT), enabling non-interactive pushes to microsoft/homebrew-msstore-cli.
Changes:
- Switches Git authentication to
x-access-tokenstyle credentials for GitHub HTTPS operations. - Adds PAT environment injection to the “Git operations” task and pushes using an authenticated URL.
File summaries
| File | Description |
|---|---|
| .pipelines/publish_release.yml | Adjusts Homebrew tap checkout/push Git commands to use a PAT for authenticated operations. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 2
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
There was a problem hiding this comment.
🟢 Approval recommended
The changes are narrow, align with the stated pipeline auth failure, and correctly scope PAT usage to the push step with a fast-fail check.
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0 new
- Review effort level: Lite
|
Approved |
Pipeline fails with auth issue at Git operations step with Authentication failure. So trying with using the PAT token in the push command